Can I replace my MultiModem® iSMS smoothly with a brevis.one SMS Gateway?
The 2G network cut-off and various functions of the brevis.one SMS Gateway are good reasons to think about a change. We strive to make the change as easy as possible.
At the beginning follow our Quick Start Guide for the first steps with the SMS Gateway.
Setting up users
In the follow-up you should set up the users for a seamlessly replace of the MultiModem® iSMS. Log in at the web interface of your MultiModem® iSMS. You will find an overview of the existing users under SMS Services - Users.
Instructions how to set up these users at the brevis.one SMS Gateway you will find here.
Grant at least the following permissions to send SMS via the web interface and the HTTP API:
- Access to the web interface
- Access to the HTTP API
You should also import the contacts of the addressbook of your MultiModem® iSMS (SMS Services - Address Book) and groups (SMS Services - Groups).
HTTP API
All functions of the HTTP API of the MultiModem® iSMS are also provided by the brevis.one SMS Gateway.
The brevis.one SMS Gateway accepts API calls on the ports 80 and 443. Proceed the following steps to find out which API port is configured in your MultiModem® iSMS:
- Log in at the web interface of the MultiModem® iSMS
- Navigate to SMS Services - SMS API
If the HTTP Port under HTTP API Configuration is configured to 80 or 443, you can use the API as usual:
http://192.168.1.1:80/sendmsg?text=Test&to=00491701234567&user=apiuser&passwd=secret&cat=1
The parameter cat is optional and only accepts the value 1.
If an error occurs, you will get one of the following error codes:
error code | Description |
601 | Authentication failed |
602 | Parse error |
603 | Invalid category |
604 | SMS message size is greater than 160 chars |
605 | Recipient overflow |
606 | Invalid recipient |
607 | No recipient |
608 | MultiModem® iSMS is busy, can’t accept this request |
609 | Timeout waiting for a TCP API request |
610 | Unknown action trigger |
611 | Error in broadcast trigger |
612 | System error - memory allocation failure |
613 | Invalid modem index |
614 | Invalid device model number |
615 | Invalid encoding type |
616 | Invalid time/date input |
617 | Invalid count input |
618 | Service not available |
619 | Invalid addressee receive |
620 | Invalid priority value |
621 | Invalid SMS text |
(Only the yellow colored messages can occur at the brevis.one SMS Gateway)
Further information about the HTTP API is provided here.
Connection to Nagios or Icinga
If you already connected your MultiModem® iSMS to your monitoring system with the script sendsms.pl from the Netways isms Nagios Plugin, you have to update it to the latest version.
i The latest script can be downloaded here: sendsms.pl.
Please consider the references to the HTTP API. If you configured a deviant HTTP Port, the script sendsms.pl needs to be adjusted.
Acknowledge problems
To acknowledge problems via SMS you will need to configure a rule in the Message Routing of the brevis.one SMS Gateway. This function requires the licensing of the Message Routing module.
- Log in at the web interface of the MultiModem® iSMS.
- Navigate to SMS Services - SMS API.
- Note down or print out the configuration under Non Polling Receive API Configuration:
- Server
- Port
- Server Default Page
- Log in at the web interface of the brevis.one SMS Gateway.
- Navigate to Configuration - Message Routing.
- Add a new rule.
- Use HTTP Request (iSMS Protokoll) as destination.
Fill in the URL to the script smsack.cgi.
The URL results from the noted configuration: http://<Server>:<Port><Server Default Page>
Network
At least configure the networking settings.
- Log in at the web interface of the MultiModem® iSMS.
- Navigate to Network Setup in the top menu.
- Note down or print out the network settings.
- Disconnect the MultiModem® iSMS from from the power supply.
- Log in at the web interface of the brevis.one SMS Gateway.
- Navigate to Configuration - Network.
- Configure the network settings as you noted them down.
- After clicking the Save button you need to restart the SMS Gateway.
That's it! Your brevis.one SMS Gateway now assumes all tasks from the MultiModem® iSMS.
i Multi-Tech®, MultiModem® and iSMS® are registered trademarks of Multi-Tech Systems, Inc. in Mounds View, Minnesota.
Related articles